Bump pnpm/action-setup to v6.0.8 to fix Node version CI failure#5939
Merged
akolson merged 1 commit intoMay 27, 2026
Merged
Conversation
v6.0.3 carries a regression (pnpm/action-setup#225, learningequality#227) that ignores the packageManager-pinned pnpm version and installs pnpm 11, which requires Node.js >=22.13 and fails on our Node 20 runners. v6.0.7 restored self-update to the packageManager-pinned version (10.33.0). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6 tasks
8 tasks
rtibblesbot
approved these changes
May 27, 2026
Contributor
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
Minimal, targeted CI fix with green CI confirming the regression is resolved.
CI: all 12 checks passing. No UI files changed — Phase 3 skipped.
- praise: All six
pnpm/action-setupoccurrences across five workflow files bumped consistently — no stale pinned versions left behind (see inline).
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
| - uses: actions/checkout@v6 | ||
| - name: Use pnpm | ||
| uses: pnpm/action-setup@v6.0.3 | ||
| uses: pnpm/action-setup@v6.0.8 |
Contributor
There was a problem hiding this comment.
praise: Every pnpm/action-setup usage across all five workflow files gets the same bump — no workflow was left on the broken v6.0.3. Good completeness check.
akolson
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CI was failing because
pnpm/action-setup@v6.0.3ignores the pinned pnpm version and installs pnpm 11, which needs Node ≥22.13 and breaks on our Node 20 runners (#225, #227). v6.0.8 has the upstream fix, restoring pnpm 10.33.0.References
Reviewer guidance
Confirm CI is green here — the "Use pnpm" step should install pnpm 10.33.0 (not 11), and no job should warn
requires at least Node.js v22.13. The upstream issues are still open, so if any job still pulls pnpm 11, the fallback is pinning tov5.AI usage
Used Claude Code to diagnose the CI failures — tracing them to the
pnpm/action-setupv6 regression by reading the action source and the upstream issue tracker — and to apply the version bump. Confirmed v6.0.8 contains the upstream fix before selecting it.